chore(eql): repoint manifests at cipherstash/stack - #937
Merged
Conversation
npm and crates.io both reject a publish whose manifest repository field doesn't match the publishing repository. Trusted publishing for @cipherstash/eql and eql-bindings is now configured against cipherstash/stack, but the manifests still named cipherstash/encrypt-query-language — so a release triggered from here would fail regardless. Repoints package.json (repository.url, repository.directory, bugs.url) and eql-bindings' Cargo.toml (repository, homepage), and adds a guard test mirroring ffi-repository-urls.test.mjs so this can't regress silently. release-plz.toml's prose was checked and needs no change — it doesn't reference the old repository.
🦋 Changeset detectedLatest commit: e52d331 The changes in this PR will be included in the next version bump. This PR includes changesets to release 12 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
freshtonic
approved these changes
Aug 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Trusted publishing for
@cipherstash/eql(npm) andeql-bindings(crates.io) is now configured againstcipherstash/stack, but the manifests themselves still namedcipherstash/encrypt-query-language. Both npm and crates.io reject a publish whose manifestrepositoryfield doesn't match the publishing repository, so a release triggered from here today would fail. This is the last blocker before EQL can actually release fromcipherstash/stack— the "trusted publishing points at stack" step alone isn't the same as "a release can succeed here."Changes
packages/eql/packages/eql/package.json:repository.url→git+https://github.com/cipherstash/stack.git,repository.directory→packages/eql/packages/eql(the npm package's real location under the verbatim-prefix subtree import),bugs.url→https://github.com/cipherstash/stack/issues.packages/eql/crates/eql-bindings/Cargo.toml:repositoryandhomepage→https://github.com/cipherstash/stack.scripts/__tests__/eql-repository-urls.test.mjs, mirroringffi-repository-urls.test.mjs, so a regression here fails CI instead of a future publish.release-plz.toml's prose — it doesn't reference the old repository, so it needed no change.Verification
npx vitest run --config scripts/vitest.config.mjs scripts/__tests__/eql-repository-urls.test.mjs— 5/5.pnpm run code:fix(Biome) run scoped to the changed files — no other issues.lint-no-eql-registry-pins.test.mjs,cargo-lock-freshness.test.mjs,bench-index-expressions.test.mjs) — confirmed pre-existing onmainviagit stash, not caused by this PR.Related
Part of the EQL →
cipherstash/stacktrusted-publishing cutover.